Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linter improvements #117

Merged
merged 2 commits into from
Mar 15, 2022
Merged

Linter improvements #117

merged 2 commits into from
Mar 15, 2022

Conversation

mantzas
Copy link
Contributor

@mantzas mantzas commented Mar 14, 2022

Which problem is this PR solving?

Linter improvements.

Short description of the changes

  • Switched to cfg based linting
  • Fixed linting issues
  • Upgraded linter

@mantzas mantzas marked this pull request as ready for review March 14, 2022 07:24
Copy link
Contributor

@c0nstantx c0nstantx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a small comment. You can ignore it

@@ -163,7 +163,7 @@ func (s *Seeder) Seed(cfg *config.Config) error {
// the parsing won't stop, and we make sure we try to parse every flag passed when running the command.
for _, arg := range os.Args[1:] {
if err := flagSet.Parse([]string{arg}); err != nil {
// Simply log errors that can happen, such as parsing unexpected flags. We want this to be silent
// Simply log errors that can happen, such as parsing unexpected flags. We want this to be silent,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very naive comment, but would it be better to move the comment after the period (.) to the next line ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no guideline for that. Personally I am optimizing for vertical space and only go to the next line if the content does not fit the width. More can be displayed this way, l;less scrolling.

@mantzas mantzas merged commit 0b626f5 into master Mar 15, 2022
@mantzas mantzas deleted the linter-improvements branch March 15, 2022 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants